Network element managing system

ABSTRACT

A network element managing system includes a management control section for maintaining and managing network elements such as an exchange or a telecommunication line and a communication control section for controlling the communication processing of the network so that an interface is commonly used between the management control section and the communication control section, thereby satisfying a required performance in both of a processing request relating to maintenance, management and operation and a processing request relating to communication. That is, the system of the invention includes a scheduling section for determining execution order on the basis of the attribute of the processing request, and the loads of the communication control section and the management control section. Also, the communication control section and the management control section have a function for scheduling the processing request on the basis of the attribute of the object to be processed, respectively.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a system for controlling, maintainingand managing network elements consisting of an exchange, atelecommunication line and so on.

2. Background of the Invention

In general, a telecommunication network is made up of network elementssuch as an exchange, a switching office, a subscriber's line, atransmission line, a power supply equipment and the like, and a systemfor maintaining and managing those network elements.

The system for maintaining and managing the network elements iscomprised of a manager system for integrally managing a plurality ofnetwork elements and an agent system for maintaining the respectivenetwork elements.

The agent system is provided with a function for executing themonitoring, examination, control, fault-restoration, equipmentoperation, etc. of the respective network elements in accordance with aninstruction from the manager system. The agent system is furtherprovided with a function for collecting and storing the operationhistories of the respective network elements under monitoring orexamination and for notifying the manager system of those operationhistories.

On the other hand, in a communication processing (service control) suchas setting or releasing of a path, there is a technique for separatingan exchange function and a service control function as in an intelligentnetwork. In the technique, the service control system forwards aninstruction to an exchange system so that the exchange system provides arequired service.

However, the maintaining/managing system is independent from the servicecontrol system, to thereby require a communication device every system.Moreover, this causes both the systems to reserve and manage datarelating to the network elements and the like.

Further, in recent years, the rising expectation that the communicationservice is highly developed requires service control (ormaintenance/management) based on information relating to both of themaintenance/management and service control. However, the independence ofthe maintenance/management system from the service control system makesit difficult to mutually refer to information.

SUMMARY OF THE INVENTION

An object of the present invention is to provide a technique effectivein realizing common device or data and a complicated and highly advancedservice due to mutual cooperation.

In order to solve the foregoing problem, the present invention providesa system for controlling, maintaining and managing network elements suchas an exchange and a telecommunication line in which an interfacebetween a manager system and an agent system is made common to aninterface between a service control system for a communication serviceand an exchange system. With this structure, the system of the inventionallows the common interface to perform the service control and themaintenance/management.

In other words, a network element managing system of the presentinvention includes managing means and agent means, in which the managermeans serves as a system for allowing the network elements to executeservice control and maintenance/management through the agent means.

In detail, the manager means includes a function for issuing acommunication processing request in addition to a function for issuing aprocessing request relating to the maintenance, operation and managementof network elements.

According to such a structure of the manager means, the agent meansincludes a function for controlling a communication processing of thenetwork elements in addition to a function for executing themaintenance, operation and management of the network elements such as anexchange and a telecommunication line.

The agent means further includes a scheduling function fordiscriminating a processing relating to maintenance, operation andmanagement and a communication processing, and for executing thecommunication processing in precedence to the processing relating tomaintenance, operation and management, for executing the communicationprocessing in real time.

One example of that scheduling technique is, for example, of a techniquein which a CPU-occupied period of time assigned to a task for executingthe communication processing is longer than that assigned to a task forexecuting the processing relating to maintenance. Moreover, in thecommunication processing, a CPU-occupied period of time assigned to atask for executing a call setting processing may be made longer thanthat assigned to a task for a setting release processing.

Further, the agent means includes a scheduling section and an operationprocessing section.

The scheduling section is provided with a function fortransmitting/receiving data to/from the manager means and a function fordiscriminating whether the processing request from the manager means isa processing request relating to the maintenance/management of a networkor a processing request relating to the communication processing todetermine a precedence of the processing requests.

The operation processing section includes a function for determining aprocessing request in accordance with the precedence determined by thescheduling section. The operation processing section includes acommunication control section for executing the processing requestrelating to a communication and a management control section forexecuting the processing request relating to the maintenance/management.

Furthermore, the communication control section includes an objectmanagement table for registering a resource identification informationspecifying the respective resources within the network and an objectidentifier where each resource has been converted into a logic model.

On the other hand, the management control section includes a object datastoring section for storing a resource identifier specifying therespective resources within the network, an object identifier where eachresource has been converted into a logic model, and attribute data ofthe respective resources.

The network element managing system with the foregoing structure selectsan appropriate network element from the position of a subscriber whenthe manager means receives a predetermined call setting request betweenthe subscribers from a specific subscriber, for example, an informationprovider of an information providing service to transmit a processingrequest to the agent means for the selected network element.

The scheduling section of the agent means analyzes the processingrequest and discriminates whether it is a processing request relating tothe communication processing or a processing request relating to themaintenance. Further, the agent means assigns an execution time inaccordance with a precedence degree of the processing request. Indetail, the scheduling section assigns an unoccupied period of time of aCPU as an execution time if the processing request is a processingrequest relating to maintenance, but assigns an execution time inprecedence if it is a communication processing request.

The operation processing section starts the management control sectionin accordance with the execution time which has been determined by thescheduling section if the processing request is a processing requestrelating to maintenance/management. Then, the management control sectionexecutes the processing request and notifies the manager means of theexecution result.

Also, in the case where the processing request is a processing requestrelating to communication, the operation processing section starts thecommunication control section in accordance with an instruction from thescheduling section. Then, the communication control section converts theprocessing request into a command form which is capable of beingprocessed by the network element to allow the network element to executethe requested processing. Further, the communication control sectionnotifies the manager means of the execution result of the processingrequest.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing the respective functional structuresof a network element managing system in accordance with a firstembodiment of the present invention;

FIG. 2 is a schematic structural diagram showing a communication networkto which a network element managing system in accordance with a secondembodiment of the present invention is applied;

FIG. 3 is a block diagram showing the respective functional structuresof an agent system;

FIG. 4 is a diagram showing an example of an object managing table;

FIG. 5 is a diagram showing an example of an object data base;

FIG. 6 is a diagram showing a sequence 1 of a network element managingsystem in a call setting operation;

FIG. 7 is a diagram showing an image of a call setting processingcorresponding to the sequence of FIG. 6;

FIG. 8 is a diagram showing a sequence 2 of a network element managingsystem in a call setting operation;

FIG. 9 is a diagram showing an image of a call setting processingcorresponding to the sequence of FIG. 8;

FIG. 10 is a diagram showing a sequence 3 of a network element managingsystem in a call setting operation;

FIG. 11 is a diagram showing an image of a call setting processingcorresponding to the sequence of FIG. 10;

FIG. 12 is a block diagram showing the respective functional structuresof an operation processing section in accordance with a third embodimentof the present invention;

FIG. 13 is an explanatory diagram showing a data renewal processing in acommunication service executing section;

FIG. 14 is a diagram showing the state transition of a lockidentification flag of the object managing table in the operation ofFIG. 13;

FIG. 15 is an explanatory diagram showing a data renewal processing in amaintenance service executing section;

FIG. 16 is a diagram showing the state transition of a lockidentification flag of an object data base in the operation of FIG. 15;

FIG. 17 is a diagram showing one example of a data structure of anobject data base;

FIG. 18 is a diagram showing one example of a data structure of anobject managing table;

FIG. 19 is an explanatory diagram showing a designated procedure of anobject;

FIG. 20 is a flowchart showing the operation of a high-precedenceprocessing unit in a communication service executing section;

FIG. 21 is a flowchart showing the operation of a low-precedenceprocessing unit in the communication service executing section;

FIG. 22 is a flowchart showing the operation of a high-precedenceprocessing unit in the maintenance service executing section;

FIG. 23 is a flowchart showing the operation of a low-precedenceprocessing unit in the maintenance service executing section;

FIG. 24 is a block diagram showing the respective functional structuresof an operation processing section in accordance with a fourthembodiment of the present invention;

FIG. 25 is a diagram showing an example of an object attribute table;

FIG. 26 is a diagram showing an example of an object precedence degreetable;

FIG. 27 is a diagram showing an example of an action precedence degreetable;

FIG. 28 is a flowchart showing the operation of a communication serviceexecuting section; and

FIG. 29 is a diagram showing another structure of a communicationservice executing section.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

(First Embodiment)

FIG. 1 is a block diagram showing the respective functional structuresof a network element managing system in accordance with a firstembodiment of the present invention.

The network element managing system includes a manager system 1 and anagent system 2. The agent system 2 is provided with a function forconverting, upon reception of a communication processing request fromthe manager system 1, the processing request into a command form whichis capable of being processed by an exchange 3 to allow the exchange 3to execute the requested processing.

In detail, the manager system 1 includes a function for issuing acommunication processing request in addition to a function for issuing aprocessing request relating to the maintenance, operation and managementof network elements.

Correspondingly to the manager system 1, the agent system 2 includes afunction for controlling a communication processing of an exchange 3 inaddition to a function for executing the maintenance, operation andmanagement of the network elements such as the exchange 3 and atelecommunication line.

The agent system 2 further includes a scheduling section 2a and anoperation processing section 2b.

The scheduling section 2a is provided with a function fordiscriminating, upon reception of a processing request, whether theprocessing request is a request relating to maintenance, operation andmanagement or a request relating to communication. Further, thescheduling section 2a has a function for determining a precedence orderof the respective processing request processing in accordance with theattribute of the processing request. Concretely, the scheduling section2a gives a precedence order higher than that of the processing requestrelating to maintenance, operation and management to the processingrequest relating to communication.

The operation processing section 2b is provided with a function forexecuting the processing request in accordance with an execution timewhich has been determined by the scheduling section 2a. Concretely, theoperation processing section 2b includes a communication control section20 and a management control section 21.

The communication control section 20 has a function for allowing theexchange 3 to execute the processing request relating to communicationand for notifying the manager system 1 of the execution result. Indetail, the communication control section 20 has a function forconverting the processing request relating to communication into acommand form which is capable of being processed by the exchange 3, afunction for allowing the exchange 3 to execute the processing requestthus converted, and a function for notifying the manager system 1 of theexecution result of the processing request. The communication controlsection 20 further includes an object managing table 20a for storingtherein a resource identifier for specifying the respective resourceswithin a network and an object identifier where each resource has beenconverted into a logic model.

The management control section 21 has a function for executing aprocessing request relating to the maintenance/management of the networkto notify the manager system 1 of the execution result. The managementcontrol section 21 also includes an object managing table 21a forstoring therein a resource identifier for specifying the respectiveresources within the network, an object identifier where each resourcehas been converted into a logic model, and attribute data of therespective resources.

Hereinafter, a description will be given of the operation of a networkelement managing system in accordance with a first embodiment of thepresent invention.

The manager system 1 selects, upon reception of a call setting requestbetween predetermined subscribers from information provider of aninformation providing service, an appropriate network element from theposition of the subscriber and transfers a processing request to theagent system 2 of that network element.

The scheduling section 2a of the agent system 2 analyzes the processingrequest and discriminates whether it is a processing request relating toa communication processing or a processing request relating tomaintenance. In accordance with the discrimination result, thescheduling section 2a determines a precedence order of the processingrequest and starts the operation processing section 2b.

The operation processing section 2b starts the management controlsection 21 in accordance with the precedence order which has beendetermined by the scheduling section 2a if the processing request is aprocessing request relating to maintenance. The management controlsection 21 executes the processing request.

On the other hand, if the processing request is a processing requestrelating to a communication processing, the operation processing section2b starts the communication control section 20 immediately.

The communication control section 20 converts the processing processinto a command form which is capable of being processed by the exchange3 and notifies the exchange 3 of it.

The operation processing section 2b notifies the manager system 1 of theexecution result of the communication control section 20 or theexecution result of the management control section 21.

As described above, according to the first embodiment of the invention,the system for maintaining and managing the network element can executethe communication processing in real time.

(Second Embodiment)

Hereinafter, a description will be given of a second embodiment of thepresent invention with reference to the drawings.

FIG. 2 is a schematic structural diagram showing a communication networkto which a network element managing system is applied.

The network element management system of this embodiment is designed soas to connect a manager system 4 and an exchange managing section 6through an interface section 5, and connect an exchange 7 to theexchange managing section 6.

The interface section 5 is formed of an MO (managed object) interfacewhich has been conducting a standardization action even in an ISO orITU-T (old CCITT) at the present time. A CMIP is adopted as thecommunication protocol of the manager system 4 and the exchange managingsection 6.

In this example, the manager system 4 has a function for issuing acommunication service request and a maintenance service request to theexchange managing section 6. In detail, the manager system 4 is providedwith call control functions such as a signal terminal, routine,subscriber/service analysis, issuance of a communication service requestof network functions necessary for realizing a line connection service.

The exchange managing section 6 includes an agent system 6a and anapplication processing section 6b. The agent system 6a executes aservice request from the manager system 4, and the applicationprocessing section 6b executes a maintenance service of the exchange 7independently from the manager system 4 through application softwarewhich has been previously registered therein.

Furthermore, the exchange 7 is equipped with an exchange resourcecontrol section 7a for controlling the operation of an exchangeresource. The exchange resource control section 7a is comprised of aplurality of routines for executing the control order of a variety ofexchange resources, which does not depend on the attribute of a service.The control order is, for example, of a line capture order, a pathcapture order, a path connection order, a system change-over order.

In this example, in the case of introducing the foregoing networkelement managing system to a network which does not support the MOinterface, an application for controlling a resource by successivelystarting the foregoing order is structured within the system of thisembodiment.

Subsequently, a description will be given of the function of the agentsystem 6a with reference to FIG. 3. FIG. 3 is a block diagram showingthe respective functional structures of the agent system, and the agentsystem 6a according to the second embodiment is equipped with aninterface end portion 60, an execution scheduling section 61, and anoperation processing section 62.

The interface end portion 60 is arranged to process the communicationprotocol of data delivered between the manager system 4 and theexecution scheduling section 61.

The execution scheduling section 61 analyzes the service request fromthe manager system 4 and discriminates whether the service request inquestion is of a maintenance service request or a communication servicerequest. The execution scheduling section 61 determines a precedenceorder of the service requests in accordance with the kind of theservice. Concretely, the execution scheduling section 61 determines aCPU-occupied time which is assigned to the execution task of the variousservices. In particular, since the communication service such as a callconnection service is necessarily processed in real time, theCPU-occupied time longer than that assigned to the maintenance serviceexecution task is assigned to the communication service.

The operation processing section 62 is arranged so as to process theservice request on the basis of an execution time assigned to theexecution scheduling section 61, and include a communication serviceexecuting section 63 and a maintenance service executing section 64.

The communication service executing section 63 is equipped with afunction for converting a communication service request from the managersystem 4 into a command form which is capable of being processed by theexchange resource control section 7a, and a function for operating theexchange resource control section 7a in accordance with the executiontime to execute the communication service request. In detail, thecommunication service executing section 63 includes an object managingsection 63a and an object interface processing section 63b. The objectmanaging section 63a has an object managing table (refer to FIG. 4) forregistering a correspondence between the resource identifiers of therespective resources and the objects where the respective resources havebeen converted into logic models.

The object interface processing section 63b has a function forconverting data received from the object managing section 63a into alanguage form which is capable of being processed by the exchangeresource control section 7a, and a function for converting data receivedby the exchange resource control section 7a into a language form whichis capable of being processed by the object managing section 63a.

The maintenance service executing section 64 includes an object database 64a (refer to FIG. 5) for storing resource identifiers andattribute information of the respective resources every objectidentifier.

Hereinafter, a description will be given of an operation process of thenetwork element managing system in accordance with the secondembodiment, referring to an example where a call is set between aterminal A (8a) and a terminal B (8b).

In FIG. 6, when the manager system 4 issues a line end terminal captureorder of the terminal A (8a), the interface end portion 60 converts theprotocol of that order and notifies the execution scheduling section 61of it in the agent system 6a.

The execution scheduling section 61 analyzes the order in question anddiscriminates whether it is a communication service request or amaintenance service request. In this example, since the order inquestion is of a line terminal capture order (communication servicerequest), the execution scheduling section 61 assigns a high precedenceorder to the order in question and notifies the communication serviceexecuting section 63 of the operation processing section 62 of the orderin question.

In the communication service executing section 63, the object managingsection 63a analyzes the order in question and discriminates thatrequest contents are of a capture request for a communication line endterminal.

Concretely, the manager system 4 transmits a line capture order to whicha "TP" where the end terminal of the communication line has beenconverted into an object and a reception number of the terminal A (8a)have been added to the object managing section 63a. The object managingsection 63a extracts the object "TP" of the line end terminal from theline capture order and assigns an object identifier "TP-#1" foridentifying the respective line end terminals to the line end terminal.Simultaneously, the object managing section 63a discriminates a sourcename "TANSI" of the object "TP", and notifies the object interfaceprocessing section 63b of the object identifier "TP-#1" and the resourcename "TANSI". The object interface processing section 63b converts theline capture order into a language form which is capable of beingprocessed by the exchange resource control section 7a on the basis ofthe resource name "TANSI" and the reception number, and transmits theconverted order to the exchange resource control section 7a.

Upon reception of the line capture order, the exchange resource controlsection 7a discriminates the line end terminal of the terminal A (8a)from the reception number of the terminal A (8a), and monitors aswitching circuit of the exchange 7 to discriminate whether the line endterminal is in an unoccupied state, or not. If it is in the unoccupiedstate, the exchange resource control section 7a captures that line endterminal (refer to FIG. 7), and transmits the resource ID "TANSI-1" ofthe line end terminal to the agent system 6a.

In the agent system 6a, the communication service executing section 63receives the resource ID "TANSI-1". In the communication serviceexecuting section 63, the object interface processing section 63bnotifies the object managing section 63a of the object identifier"TP-#1" and the resource ID "TANSI-1" before notifying the maintenanceservice executing section 64 of the resource ID "TANSI-1" of the lineend terminal, the object identifier "TP-#1" assigned to the line endterminal and the attribute information of the line end terminal.

In this example, the maintenance service executing section 64 updatesthe object data base 64a on the basis of the object identifier "TP-#1",the resource ID "TANSI-1" and the attribute information.

On the other hand, the object managing section 63a notifies theexecution scheduling section 61 of the object identifier "TP-#1" as wellas a notice of the line capture completion simultaneously whileregistering the object identifier "TP-#1" and the resource ID "TANSI-1"in the object managing table. The execution scheduling section 61transmits the object identifier "TP-#1" and a notice of the line capturecompletion to the manager system 4.

Subsequently, the manager system 4 transmits the line end terminalcapture order of the terminal B (8b). The agent system 6a processes theline end terminal capture order. The processing procedure will bedescribed with reference to a sequence shown in FIG. 8.

In the agent system 6a, the interface end portion 60 subjects the orderfrom the manager system 4 to a protocol processing to notify theexecution scheduling section 61 of the processed order.

The execution scheduling section 61 analyzes the order, recognizes thatthe order is a line end terminal capture order, and assigns a highprecedence order to that order. Then, the execution scheduling section61 notifies the communication service executing section 63 in theoperation processing section 62 of that order.

In the communication service executing section 63, the object managingsection 63a analyzes that order, extracts the "TP" where the line endterminal has been converted into an object from the order, and assignsan object identifier "TP-#2" for identifying the respective line endterminals to the line end terminal. Simultaneously, the object managingsection 63a discriminates the source name "TANSI" of the object "TP",and notifies the object interface processing section 63b of the objectidentifier "TP-#2" and the resource name "TANSI".

The object interface processing section 63b converts the line captureorder into a language form which is capable of being processed by theexchange resource control section 7a on the basis of the resource name"TANSI" and the reception number of the terminal B (8b), and transmitsit to the exchange resource control section 7a.

Upon reception of the line capture order, the exchange resource controlsection 7a discriminates the line end terminal of the terminal B (8b)from the reception number of the terminal B (8b), and monitors aswitching circuit in the exchange 7 to discriminate whether the line endterminal is in an unoccupied state, or not. If it is in the unoccupiedstate, the exchange resource control section 7a captures the line endterminal (refer to FIG. 9), and transmits the resource ID "TANSI-2" ofthe line end terminal to the agent system 6a.

In the agent system 6a, the communication service executing section 63receives the resource ID "TANSI-2". In the communication serviceexecuting section 63, the object interface processing section 63bnotifies the object managing section 63a of the object identifier"TP-#2" and the resource ID "TANSI-2" before notifying the maintenanceservice executing section 64 of the resource ID "TANSI-2" of the lineend terminal, the object identifier "TP-#2" assigned to the line endterminal and the attribute information of the line end terminal.

In this example, the maintenance service executing section 64 updatesthe object data base 64a on the basis of the object identifier "TP-#2",the resource ID "TANSI-2" and the attribute information.

On the other hand, the object managing section 63a registers the objectidentifier "TP-#2" and the resource ID "TANSI-2" in the object managingtable, and simultaneously notifies the execution scheduling section 61of the object identifier "TP-#2" as well as a notice of the line capturecompletion. The execution scheduling section 61 transmits the objectidentifier "TP-#2" and the notice of the line capture completion to themanager system 4.

Further, upon the recognition of the capture of the line end terminal ofthe terminal A (8a) and the line end terminal of the terminal B (8b),the manager system 4 transmits a capture request for a path connectingthose line end terminals to the agent system 6a. Concretely, the managersystem 4 transmits to the agent system 6a the connection path captureorder for those line end terminals together with the object identifiers"TP-#1" and "TP-#2" of the line end terminals to be connected.Hereinafter, a description will be given of a processing procedure ofthe agent system 6a with reference to a sequence shown in FIG. 10.

In the agent system 6a, the interface end portion 60 converts theprotocol of the order and notifies the execution scheduling section 61of the converted order.

The execution scheduling section 61 analyzes the order, recognizes thatit is a path connection request, and assigns a high precedence order tothat order. Then, the execution scheduling section 61 notifies thecommunication service executing section 63 of that order.

In the communication service executing section 63, the object managingsection 63a analyzes that order and discriminates that the requestedcontents are of a request for connecting a path between the line endterminals "TP-#1" and "TP-#2". Thereafter, an object identifier "XC#1"is assigns to a path to be connected. Moreover, the object managingsection 63a discriminates the resource name "PATH" of the path as wellas the resource IDs "TANSI-1" and "TANSI-2" of the line end terminals"TP-#1" and "TP-#2", and notifies the object interface processingsection 63b of the object identifiers "XC-#1" and the resource name"PATH" of the path, and the object identifier "TP-#1", "TP-#2" and theresource IDs "TANSI-1" and "TANSI-2" of the line end terminal.

The object interface processing section 63b converts the path connectionorder into a language form which is capable of being processed by theexchange resource control section 7 on the basis of the source name"PATH" and the resource IDs "TANSI-1" and "TANSI-2" of the line endterminal, to transmit the order to the exchange resource control section7a.

Upon the reception of the path connection order, the exchange resourcecontrol section 7a monitors the state of the switch circuit anddiscriminates whether there exists a path which is capable of connectingthe line end terminal "TANSI-1" and the line end terminal "TANSI-2", ornot. If there is such a path, the exchange resource control section 7acaptures the path (refer to FIG. 11) and transmits the resource IDs"PATH-0001" of the path to the agent system 6a.

In the agent system 6a, the communication service executing section 63receives the resource ID "PATH-0001". In the communication serviceexecuting section 63, the object interface processing section 63bnotifies the object managing section 63a of the object identifier"XC-#1" and the resource ID "PATH-0001" before notifying the maintenanceservice executing section 64 of the resource ID "PATH-0001" of thispath, the object identifier "XC-#1" assigned to the path and theattribute information of the line end terminal.

In this example, the maintenance service executing section 64 updatesthe object data base 64a on the basis of the object identifier "XC-#1",the resource ID "PATH-0001" and the attribute information of the path.

On the other hand, the object managing section 63a registers the objectidentifier "XC-#1" and the resource ID "PATH-0001" in the objectmanaging table, and simultaneously notifies the execution schedulingsection 61 of the object identifier "XC-#1" and a notice of the pathconnection completion. In this situation, the execution schedulingsection 61 transmits the object identifier "XC-#1" and the notice of thepath connection completion to the manager system 4 through the interfaceend terminal 60.

As described above, according to the second embodiment, thecommunication service request issued from the manager system 4 can beexecuted in real time, and the consistency between the object managingtable and the object data base 64a can be held.

(Third Embodiment)

FIG. 12 is a block diagram showing the respective functional structuresof an operation processing section 62 in accordance with a thirdembodiment of the present invention.

The operation processing section 62 is made up of the communicationservice executing section 63 and the maintenance service executingsection 64 as in the foregoing first embodiment.

(Structure of Communication Service Executing Section 63)

The communication service executing section 63 is equipped with a highprecedence processing section 63c and a low precedence processingsection 63d in addition to the structure of the foregoing firstembodiment.

The high precedence processing section 63c is arranged to executeprocessing requiring a high-speed property. Concretely, the highprecedence processing section 63c is provided with a function forexecuting a data renewal request from the manager system 4 or the lowprecedence processing executing section 64d within the maintenanceservice executing section.

The low-precedence processing executing section 63d is arranged toexecute processing requiring no high-speed property. Concretely, thelow-precedence processing executing section 63d has a function forexecuting a processing request from the maintenance service executingsection 64.

The high-precedence processing executing section 63c and thelow-precedence processing executing section 63d have a function which isrealized by making the CPU execute the program module. Then, the programmodule of the high-precedence processing executing section 63c can usethe CPU in precedence to the program module of the low-precedenceprocessing executing section 63d. Therefore, upon the reception of aprocessing request, the high-precedence processing executing section 63ccan execute the processing request immediately. On the other hand, thelow-precedence processing executing section 63d executes the processingwhen the load of the CPU is small, that is, in the intervals of theprocessing of the high-precedence processing executing section 63c.

The low-precedence processing executing section 63d is provided with afunction for executing a plurality of processing in parallel since nohigh-speed processing is required.

The object managing table 630 according to the third embodimentregisters an in-device lock identification flag and an out-of-devicelock identification flag every data. The in-device lock represents astate of prohibiting access to the respective data from the interior ofthe communication service executing section 63. The in-device lockidentification flag is of a flag for identifying whether access to therespective data from the interior of the communication service executingsection is in a prohibiting state, or not.

On the other hand, the out-of-device lock shows a state of prohibitingaccess to the respective data from the exterior of the communicationservice executing section. The out-of-device lock identification flag isof a flag for identifying whether access to the respective data from theexterior of the communication service executing section is in aprohibiting state, or not.

Further, the object managing section 63a is equipped with a function forlocking data to be updated inside of the device while locking the dataoutside of the device, and a function for rewriting the contents oflocked data in accordance with the renewal request.

Next, a description will be given of the detailed functions of theforegoing respective sections with reference to FIG. 13.

Upon reception of a renewal request of the object managing table 630from the manager system 4, the high-precedence processing executingsection 63c discriminates data to be updated. The high-precedenceprocessing executing section 63c requests the object managing section63a to lock data to be updated.

Upon reception of a request of locking data from the high precedenceprocessing executing section 63c, the object managing section 63a gainsaccess to the object managing table 630 and rewrites the in-device lockidentification flag of the data into a lock state, and simultaneouslyrewrites the out-of-device lock identification flag into a lock state.

Upon recognizing the in-device lock and the out-of-device lock, thehigh-precedence processing executing section 63c instructs the renewalof data to the object managing section 63a.

Upon reception of the renewal instruction from the high-precedenceprocessing executing section 63c, the object managing section 63arewrites data of the object managing table 630 in accordance with thatinstruction.

Moreover, upon recognizing the renewal of data, the high-precedenceprocessing executing section 63c instructs the release (in-deviceunlock) of the in-device lock to the object managing section 63a.

Upon reception of the instruction of the in-device unlock from thehigh-precedence processing executing section 63c, the object managingsection 63a rewrites the in-device lock identification flag of that datainto an unlock state.

In this situation, the high-precedence processing executing section 63cnotifies the manager system 4 which has issued the original request ofthe completion of the renewal processing.

In this example, data of the object managing table 630 is also stored inthe object data base 64a of the maintenance service executing section64. When data of the object managing table 630 is updated, theconsistency between the object managing table and the object data base64 is necessarily held. Correspondingly, the high-precedence processingexecuting section 63c has a function for notifying the maintenanceservice executing section 64 of the data renewal request upon thecompletion of the renewal processing of the object managing table 630.

In this situation, upon reception of the completion of the renewalprocessing from the maintenance service executing section 64, thelow-precedence processing executing section 63d instructs the release ofthe out-of-device lock of the data to the object managing section 63a inthe intervals of the processing of the high-precedence processingexecuting section 63c.

FIG. 14 is a diagram showing the state transition of a lockidentification flag of the object managing table in the operation ofFIG. 13.

In an initial state (timing "1"), the in-device lock identification flagand the out-of-device lock identification flag represent an unlock state("0").

Upon reception of the lock request from the high-precedence processingexecuting section 63c (timing "2"), the in-device lock identificationflag and the out-of-device lock identification flag are rewritten into alock state "1".

Subsequently, upon reception of the in-device unlock request from thehigh-precedence processing executing section 63c after the completion ofdata renewal processing (timing "4"), only the in-device lockidentification flag is rewritten into an unlock state "0". In thissituation, the out-of-device lock identification flag remains in thelock state "1".

Further, upon reception of the out-of-device unlock request from thelow-precedence maintenance service executing section 64 after thecompletion of the data renewal in the maintenance service executingsection 64 (timing "9"), the out-of-device lock identification lock isrewritten into the unlock state ("0").

(Structure of Maintenance Service Executing Section 64)

The maintenance service executing section 64 includes a data managingsection 64b, a high-precedence processing section 64c, a low-precedenceprocessing executing section 64c, and a data manager judging section 64ein addition to the structure of the foregoing first embodiment.

The high-precedence processing executing section 64c is designed toexecute the processing requiring a high-speed property. Concretely, thelow-precedence processing executing section 64d is equipped with afunction for executing a data renewal request from the manager system 4.The low-precedence processing executing section 64d is equipped with afunction for executing a plurality of processing in parallel as in theforegoing communication service executing section 63.

The data managing section 64b is equipped with a function for managingdata of the object data base 64a. Concretely, the lock/unlock of data orrewriting of data is executed in accordance with an instruction from theprecedence processing executing section 64c or the low-precedenceprocessing executing section 64d.

The data manager judging section 64e has a function for discriminatingwhether data to be updated has been also stored in the object managingtable 630 in the communication service executing section 63, or not,when it has received a data renewal request from the manager system 4.

Subsequently, a description will be given of the detailed functions ofthe foregoing respective sections with reference to FIG. 15.

Upon reception of a data renewal request from the manager system 4, themaintenance service executing section 64 starts the low-precedenceprocessing executing section 64d.

The low-precedence processing executing section 64d has a function forallowing the data manager judging section 64e to discriminate whetherdata to be updated has been also stored in the object managing table 630of the communication service executing section 63, or not.

In this situation, in the case where the data to be updated has beenalso registered in the object managing table 630, the low-precedenceprocessing executing section 64d requests the low-precedence processingexecuting section 63d of the communication service executing section 63to lock data.

Then, upon reception of a notice of a lock success from thelow-precedence processing executing section 63d in the communicationservice executing section 63, the low-precedence processing executingsection 64d instructs the data managing section 64d to lock data to beupdated.

The data managing section 64b retrieves the object data base 64a andrewrites the lock identification flag of data to be updated into a lockstate.

Upon recognition of the data lock, the low-precedence processingexecuting section 64d discriminates whether the control of the exchangeis necessary or not. If the control of the exchange is necessary, thelow-precedence processing executing section 64d transmits a controlcommand to the exchange resource control section 7a, and after receptionof a response thereto from the exchange resource control section 7a,requests the high-precedence processing executing section 63c of thecommunication service executing section 63 to execute the data renewaland the in-device unlock.

If the control of the exchange is unnecessary, the low-precedenceprocessing executing section 64d requests the high-precedence processingexecuting section 63c of the communication service executing section 63to execute the renewal of data and the in-device unlock.

Upon reception of the renewal completion of data from thehigh-precedence processing executing section 63c of the communicationservice executing section 63, the low-precedence processing executingsection 64d requests the data managing section 64d to execute therenewal of data.

The data managing section 64b updates date of the object data base 64ain accordance with an instruction from the low-precedence processingexecuting section 64d.

Upon recognition of the renewal completion of the object data base 64a,the low-precedence processing executing section 64d instructs the datamanaging section 64b to release the data lock.

The data managing section 64b retrieves the object data base 64a inaccordance with an instruction from the low-precedence processingexecuting section 64d and rewrites the lock identification flag of datainto an unlock state.

Further, the low-precedence processing executing section 64c requeststhe low-precedence processing executing section 63d of the communicationservice executing section 63 to release the out-of-device lock.

FIG. 16 is a diagram showing the state transition of a lockidentification flag of an object managing table 630 in the foregoingoperation.

In other words, the in-device lock identification flag and theout-of-device lock identification lock are in an unlock state "0" duringan initial state (timing "1").

Then, a lock request issues from the maintenance service executingsection 64 to the communication service executing section 63, and whenthe low-precedence processing executing section 63d executes the lockrequest (timing "4"), the in-device lock identification flag and theout-of-device lock identification flag are rewritten into the lock state"1".

Moreover, after the high-precedence processing executing section 63cexecutes the renewal processing of data in accordance with aninstruction from the maintenance service executing section 64 (timing"9"), only the in-device lock identification flag is rewritten into theunlock state "0".

Also, upon reception of the out-of-device unlock request from themaintenance service executing section 64 (timing "15"), theout-of-device lock identification flag is rewritten into the unlockstate "0".

Here, a description will be given of a method of designating data to beupdated.

FIG. 17 is a diagram showing a data structure of an object data base 64ain the case where a CMIP (common management information protocol) isused as the protocol of the interface end portion 60. FIG. 18 is adiagram showing a data structure of an object managing table 630 incorrespondence with FIG. 17. Here, the object managing table 630 storesthose data including an upper and lower positional relationship thereoftherein in the table format.

The respective data in the figure are of data in the form of MO (managedobject).

Here, as a method of designating data to be updated, the scope conditionand the filter condition of a CMIP can be used.

The scope condition is directed to a method of designating a fulcrumconstituting a tree structure and hierarchical number from the fulcrumto data to be updated. In other words, in FIG. 17, in the case ofdesignating data "atm Switching Element #0", data "root" which is afulcrum and the hierarchical number "2" from the data "root" aredesignated.

The filter condition is directed o a method of designating conditions ofdata to be updated. In other words, in FIG. 18, "vp TTPBid. #1" and "atmFabric #0" are stored under three hierarchies of data "root". In thissituation, in the case of designating "vp TTPBid. #1", conditions ofthis data are designated. For example, in the case of designating "vpTTPBid. #1", a data type "VPTTPId" and a value "5" of this data type aredesignated.

On the other hand, in the case of designating "atm Fabric #0", a value"0" of the data type "fabric Id" of that data is designated (refer toFIG. 19).

In this manner, data to be updated can be designated by using the scopeconditions and the filter conditions together even though a name (forexample, "vpTTPBid#1", etc.) of data to be updated is not directlydesignated.

Hereinafter, a description will be given of the data renewal processingof the communication service executing section 63 and the maintenanceservice executing section 64.

(Operation of Communication Service Executing Section 63)

First, an operation of the high-precedence processing executing section63c will be described with reference to FIG. 20.

Upon reception of the data renewal request (Step 2001), thecommunication service executing section 63 starts the high-precedenceprocessing executing section 63c.

The high-precedence processing executing section 63c discriminateswhether the requester for a data renewal request is the maintenanceservice executing section 64 or the manager system 4 (Step 2002).

When the requester for the data renewal request is the manager system 4,the high-precedence processing executing section 63c discriminates datato be updated. Then, the high-precedence processing executing section63c notifies the object managing section 63a of a data lock request(Step 2003).

Referring to a lock identification flag of the object managing table630, the object managing section 63a discriminates whether the data isin the in-device lock state, or not (Step 2004). Here, if the data is inthe in-device unlock state, the object managing section 63a rewrites thelock identification flag of the data into the lock state. Moreover, theobject managing section 63a notifies the high-precedence processingsection 63c that the data lock has succeeded.

The high-precedence processing executing section 63c transmits aresource control command to the exchange resource control section 7a ifnecessary, and instructs the object managing section 63a to execute therenewal of data after reception of a reply thereto.

The object managing section 63a updates data in accordance with aninstruction from the high-precedence processing executing section 63c(Step 2005), and notifies the high-precedence processing executingsection 63c of the completion of the data renewal.

Upon the recognition of the completion of the data renewal, thehigh-precedence processing executing section 63c instructs the objectmanaging section 63a to execute the unlock of data. The object managingsection 63a gains access to the object managing table 630 and rewritesthe lock identification flag of the data into an unlock state (Step2006).

In this situation, the high-precedence processing executing section 63ctransmits the completion of the data renewal processing to the managersystem 4 (Step 2007).

Further, the high-precedence processing executing section 63c transfersa data renewal request to the high-precedence processing executingsection 64c of the maintenance service executing section 64 (Step 2008).

When the data to be updated has already been in the in-device lock inthe foregoing step 2004, the high-precedence processing executingsection 63c notifies the manager system 4 which is a renewal requesterthat the data renewal has failed (Step 2009). In this situation, it maywait for the in-device unlock.

Further, in the foregoing step 2002, if the data requester is of themaintenance service executing section 64, the low-precedence processingexecuting section 63d succeeds in the in-device lock on the basis of therequest of the maintenance service executing section 64 (this operationwill be described later), and the high-precedence processing executingsection 63c starts the object managing section 63a to execute the daterenewal processing (Step 2010).

Upon the completion of the data renewal processing, the high-precedenceprocessing executing section 63c instructs the object managing section63a to release the data lock.

The object managing section 63a gains access to the object managingtable 630 and rewrites the in-device lock identification flag into theunlock state (Step 2011).

Upon the releasing of the in-device lock, the high-precedence processingexecuting section 63c notifies the low-precedence processing executingsection 64d of the maintenance service executing section 64 of thecompletion of the data renewal processing (Step 2012).

Subsequently, a description will be given of the operation of thelow-precedence processing executing section 63d with reference to FIG.21.

Upon reception of a processing request from the maintenance serviceexecuting section 64 (Step 2101), the low-precedence processingexecuting section 63d of the communication service executing section 63discriminates whether the processing request is of a data lock requestor a data unlock request (Step 2102).

In this situation, the data unlock request is of a request for releasingthe out-of-device lock of the object managing table 630. In other words,upon the completion of the data renewal of the object managing table630, the communication service executing section 63 releases only thein-device lock. This causes the out-of-device lock to be held.Accordingly, the maintenance service executing section 64 requests therelease of the out-of-device lock after the execution of the daterenewal request from the communication service executing section 63.

In step 2102, if the processing request is of a data unlock request, thelow-precedence processing executing section 63d discriminates data to beupdated. Then, the low-precedence processing executing section 63dstarts the object managing section 63a when the processing of thehigh-precedence processing executing section 63c is interrupted orcompleted.

The object managing section 63a retrieves the object managing table 630and rewrites the out-of-device lock identification flag of data to beupdated into the unlock state Step 2103).

Also, in step 2102, if the processing request is of a data lock request,the low-precedence processing executing section 63d instructs the objectmanaging section 63a to execute the data lock when the loads of theobject managing section 63a is low (Step 2104).

The object managing section 63a retrieves the object managing table 630and refers to the in-device lock identification flag and theout-of-device lock identification flag of the data to be updated.Thereafter, the object managing section 63a discriminates whether bothof the in-device lock identification flag and the out-of-device lockidentification flag are in the unlock state, or not (Step 2105).

If both the flags indicate the unlock state, the object managing section63a rewrites both the flags into the lock state.

If the lock processing of the data to be updated has succeeded, thelow-precedence processing executing section 63d notifies thelow-precedence processing executing section 64d of the maintenanceservice executing section 64 of the success of the lock processing (Step2106).

In step 2105, if any one of the in-device lock identification flag andthe out-of-device lock identification information is in the lock state,the low-precedence processing executing section 63d notifies thelow-precedence processing executing section 64d of the maintenanceservice executing section 64 of the failure of the lock processing (Step2107). It may wait for the success of lock.

Subsequently, a description will be given of an operation of themaintenance service executing section 64.

(The Operation of Maintenance Service Executing Section 64)

First of all, the operation of the high-precedence processing executingsection 64c will be described with reference to FIG. 22.

The high-precedence processing executing section 64c is started whenreceiving a data renewal request from the communication serviceexecuting section 63.

Upon reception of the data renewal request from the communicationservice executing section 63 (Step 2201), the high-precedence processingexecuting section 64c discriminates the data to be updated. Then, thehigh-precedence processing executing section 64c instructs the datamanaging section 64b to execute the data lock.

The data managing section 64b retrieves the object data base 64a andrewrites the lock identification flag of the data to be updated into thelock state (Step 2202).

Furthermore, the high-precedence processing executing section 64cinstructs the data managing section 64b to execute the data renewal.

The data managing section 64b updates data of the object data base 64ain accordance with an instruction from the high-precedence processingexecuting section 64c (Step 2203).

Upon the completion of data renewal processing, the high-precedenceprocessing executing section 64c instructs the data managing section 64bto release the data lock.

The data managing section 64b rewrites a data lock identification flagof the object data base 64a into the unlock state in accordance with aninstruction from the high-precedence processing executing section 64c(Step 2204).

The high-precedence processing executing section 64c instructs thelow-precedence processing executing section 63d of the communicationservice executing section 63 to release the out-of-device lock of thedata (Step 2205).

Next, an operation of the low-precedence processing executing section64d will be described with reference to FIG. 23.

The maintenance service executing section 64 starts the low-precedenceprocessing executing section 64d when receiving a data renewal requestfrom the manager system 4.

Upon reception of the data renewal request from the manager system 4(Step 2301), the low-precedence processing executing section 64drequests the data manager judging section 64e to discriminate whetherdata to be updated has been also stored in the object managing table630, or not (Steps 2302 and 2303).

In this case, when the data to be updated has been stored in the objectmanaging table 630, the low-precedence processing executing section 64drequests the low-precedence processing executing section 63d of thecommunication service executing section 63 to lock data (Step 2304).

Upon reception of a notice of notice of the data lock from thelow-precedence processing executing section 63d of the communicationservice executing section 63 (Steps 2305 and 2306), the low-precedenceprocessing executing section 64d transmits a resource control command tothe exchange resource control section 7a if necessary, and afterreceiving a reply thereto, requests the high-precedence processingexecuting section 63c of the communication service executing section 63to execute the data renewal (Step 2307).

Upon reception of a notice of completion of the data renewal from thecommunication service executing section 63 (step 2308), thelow-precedence processing executing section 64d instructs the datamanaging section 64b to execute the data renewal.

The data managing section 64b gains access to the object data base 64band rewrites data to be updated (Step 2309). Upon completion of the datarenewal processing, the low-precedence processing executing section 64drequests the low-precedence processing executing section 63d of thecommunication service executing section 63 to release the out-of-devicelock (Step 2310).

Furthermore, the low-precedence processing executing section 64dtransmits the completion of the renewal processing to the manager system4 (Step 2311).

In the foregoing step 2303, when data to be updated has not been storedin the object managing table 630, the low-precedence processingexecuting section 64d instructs the data managing section 64b to lockthe data.

The data managing section 64b gains access to the object data base 64aand rewrites the lock identification flag of data to be updated into thelock state (Step 2312).

The low-precedence processing executing section 64d transmits a resourcecontrol command to the exchange resource control section 7a if thecontrol of the exchange is necessary, and after receiving its reply,instructs the data managing section 64b to execute the data renewal(Step 2313).

After the completion of data renewal processing, the low-precedenceprocessing executing section 64d instructs the data managing section 64bto release the data lock.

The data managing section 64b gains access to the object data base 64aand rewrites the lock identification flag of data to be renewed into theunlock state (Step 2314).

Then, the low-precedence processing executing section 64d notifies themanager system 4 of the completion of the renewal processing (Step2311).

Moreover, in the foregoing step 2305, upon reception of a notice offailure of the lock processing from the communication service executingsection 63, the low-precedence processing executing section 64d noticesthe manager system 4 of a failure of the data renewal processing (Step2315).

In the third embodiment, data lock/unlock information is registered inthe object managing table, however, the object managing section 63a mayhold the data lock/unlock information, individually. Similarly, the datalock/unlock information may be registered within the object data base,or may be held by the data managing section 64b, individually.

As described above, according to the third embodiment, the processing ofthe communication service executing section requiring processing in realtime is precedent to the processing of the maintenance service executingsection so that the communication service executing section can beprocessed at a high speed. Further, in the case of updating data whichis redundantly managed by the object data base and the object managingtable, the consistency of both the data can be ensured.

(Fourth Embodiment)

A description will be given of the respective functional structures ofthe operation processing section 62 in accordance with a fourthembodiment of the present invention with reference to FIG. 24.

As the protocol of the interface end portion 60 in accordance with thefourth embodiment, a CMIP is used.

The operation processing section 62 is equipped with the communicationservice executing section 63 and the maintenance service executingsection 64 as in the foregoing second embodiment.

(Structure of Communication Service Executing Section 63)

The communication service executing section 63 of the fourth embodimentincludes an object managing table 630, a processing content analyzingsection 631, a service control processing receiving section 632, aservice processing task producing section 633, and a service taskscheduling section 634.

The service control processing receiving section 632 is equipped with afunction for receiving a processing request from the manager system 4.

The processing content analyzing section 631 analyzes the processingrequest received by the service control processing receiving section 632to discriminate an object name and a processing sort of an object (MO)to be processed. In the case of using the CMIP as the protocol of theinterface end portion 60 as in the foregoing third embodiment, aprocessing request includes a class name, an object identifier, acommand sort, the parameters of the processing contents and so on of anobject to be instructed. The commands are of 6 kinds of processingcommands including an M-CREATE for instructing the generation of anobject, an M-DELETE for instructing the deletion of the object, an M-SETfor instructing the change of attributes within the object, an M-GET forinstructing the read of the attributes within the object, an M-ACTIONfor instructing a predetermined operation to the object, and anM-EVENT-REPORT for reporting the appearance or statistic of an eventwithin the object.

Further, the processing content analyzing section 631 judges theprecedence degree of a processing request with reference to a precedencedegree table registering table 636 to be described later on the basis ofthe object name and the processing sort. The processing contentanalyzing section 631 has a function for notifying the serviceprocessing task producing section 633 of the precedence degree inaddition to the processing request.

The service processing task producing section 633 produces a processingtask 635 for executing the processing request and notifies the servicetask scheduling section 634 of the processing task 635 and theprecedence degree.

The service task scheduling section 634 determines the executing orderof the processing task 635 on the basis of the precedence degree. Inthis situation, there is a case where the processing of the processingtask 635 is interrupted because of waiting for a reception ofinformation from other devices or waiting for a reply from otherdevices. For example, in the case where the communication serviceexecuting section 63 transmits a command to the exchange 3 and waits forthe execution result from the exchange 3, the execution of theprocessing task 635 is interrupted. Then, the communication serviceexecuting section 63 restarts the execution of the processing task 635which has been interrupted at the time of receiving the execution resultfrom the exchange 3. In general, the processing restarted after theinterruption is finished in a short period of time. In view of thisfact, the service scheduling section 634 may set the precedence degreeof the processing task 635 which has been interrupted to be higher thanthat of the other processing task 635.

The object managing table 630 stores an object identifier and a resourceidentifier as well as the precedence degree registering table 636.

The precedence degree registering table 636 is provided with an objectattribute table 636a, an object precedence degree table 636b, and anaction precedence degree table 636c.

The object attribute table 636a stores the object identifier, the objectname and the precedence degree attribute data therein (refer to FIG.25).

The precedence degree attribute data is of parameter information fordetermining the precedence degree of a command to the respectiveobjects.

The object precedence degree table 636b stores the precedence degree ofa command to the respective objects every precedence degree attributedata. Concretely, the object precedence degree table 636b stores theprecedence degree of a command except for the M-ACTION and the actionprecedence degree attribute data of the M-ACTION command therein. Theaction precedence degree attribute data is of parameter information fordeciding the precedence degree of the M-ACTION to the respective objects(refer to FIG. 26).

The action precedence degree table 636c stores the contents of theM-ACTION and the precedence degree associated with the respectivecontents every precedence degree attribute data (refer to FIG. 27).

Associated with the table thus constituted, the processing contentanalyzing section 631 has a function for discriminating, when receivinga processing request, an object name and a command sort from theprocessing request. The processing content analyzing section 631retrieves the object attribute table 636a on the basis of the objectname and reads a precedence degree attribute data. The processingcontent analyzing section 631 discriminates whether the processingcommand is of an M-ACTION, or not. In the case where the processingcommand is not an M-ACTION command, the processing content analyzingsection 631 reads the precedence degree of the processing degree fromthe object precedence degree table 636b. In the case where theprocessing command is an M-ACTION command, the processing contentanalyzing section 631 reads the action precedence degree attribute datafrom the object precedence table 636b while extracting the contents ofthe action from the processing command. Then, the processing contentanalyzing section 631 gains access to the action precedence degree table636c on the basis of the action precedence degree attribute data and theaction contents to read the precedence degree of the processing command.

(Structure of Maintenance Service Executing Section 64)

The maintenance service executing section 64 may be called an OAM(operation, administration and maintenance) processing section or an OA& P (operation, administration, maintenance and provision) processingsection. The maintenance service executing section 64 includes an objectdata base 64a, an OAM processing receiving portion 640, a processingcontent analyzing section 641, an OAM processing task producing section642 and an OAM processing task scheduling 643.

The OAM processing receiving section 640 receives a processing requestfrom the manager system 4.

The processing content analyzing section 641 has a function for judginga name of an object and the sort of a command from the processingrequest. Then, the processing content analyzing section 641 has afunction for retrieving a precedence degree registering table not shownon the basis of a name of the object and the sort of a command to judgethe precedence degree of the processing request.

The OAM processing task producing section 642 has a function forproducing a processing task 644 on the basis of a name of the object andthe sort of a command.

The OAM processing task scheduling 643 has a function for determiningthe executing order of the processing tasks produced by the OAM taskproducing section 642 in accordance with the precedence degree.

In the object data base 64a, the precedence degree registering table notshown is stored as in the communication service executing section 63.

Hereinafter, a description will be given of an operation of thecommunication service executing section 63. The operation of themaintenance service executing section 64 is similar to that of thecommunication service executing section 63, and therefore itsdescription will be omitted.

(Operation of Communication Service Executing Section 63)

When the manager system 4 transmits a processing request of M-CREATE(vcCTP, DNxxx, band, QOS, . . . ) conforming to the CMIP agreement tothe agent system 6a, the interface end portion 60 decodes the processingrequest and discriminates whether the request is a processing requestrelating to communication or a processing request relating tomaintenance/management. If it is a processing request relating tocommunication, the interface end portion 60 transfers the processingrequest to the communication service executing section 63. If it is aprocessing request relating to maintenance/management, the interface endportion 60 transfers the processing request to the maintenance serviceexecuting section 64.

In this case, since the processing request of M-CREATE is a processingrequest relating to communication, the interface end portion 60transfers the processing request of M-CREATE to the communicationservice executing section 63.

Upon reception of the processing request of M-CREATE, the servicecontrol processing receiving section 632 of the communication serviceexecuting section 63 notifies the processing content analyzing section631 of the processing request of M-CREATE.

The processing content analyzing section 631 analyzes the processingrequest of M-CREATE and extracts a name of the object (Step 2801, FIG.28).

The processing content analyzing section 631 gains access to the objectattribute table 636a of the precedence degree registering table 636 onthe basis of the name of the object (Step 2802). The processing contentanalyzing section 631 reads the precedence degree attribute datacorresponding to the name of the object (Step 2803).

Subsequently, the processing content analyzing section 631 extracts thesort of commands from the processing request of M-CREATE to discriminatewhether it is of M-ACTION, or not (Step 2804).

Since the command sorts of the processing request M-CREATE is not ofM-ACTION, the processing content analyzing section 631 gains access tothe object precedence table 636b on the basis of the precedence degreeattribute data (Step 2805).

Subsequently, the processing content analyzing section 631 reads theprecedence degree of the processing request from the object precedencedegree table 636b (Step 2806), and notifies the service processing taskproducing section 633 of the processing request and the precedencedegree.

If it is judged that the sort of the processing command is of M-ACTIONin the foregoing step 2804, the processing content analyzing section 631gains access to the object precedence degree table 636b on the basis ofthe precedence degree attribute data (Step 2807).

Then, the processing content analyzing section 631 reads the actionprecedence degree attribute data from the object precedence degree table636b (Step 2808), and simultaneously reads the contents of action fromthe processing request of M-ACTION (Step 2809).

The processing content analyzing section 631 gains access to the actionprecedence degree table 636c on the basis of the contents of action andthe action precedence degree attribute data (Step 2810). The processingcontent analyzing section 631 reads the precedence degree of theprocessing request from the action precedence degree table 636c (Step2811), and notifies the service processing task producing section 634 ofthe precedence degree.

The service processing task producing section 633 produces theprocessing task 635 corresponding to the processing request, andnotifies the service task scheduling section 634 of the processing task635 and the precedence degree.

The service task scheduling section 634 determines the executing orderof the processing task 635 in accordance with the precedence degree.

The processing task 635 executes the production or registration of MO,and gains access to the resource within the exchange 3 of the networkelement correspondingly. For example, the processing task 635 requeststhe exchange 3 to capture a virtual path identifier VPI and the virtualchannel identifier VCI. Then, the processing task 635 interrupts theprocessing and waits for a reply from the exchange 3.

Upon reception of the reply from the exchange 3, the service taskscheduling 634 sets the precedence degree of the processing task 635 tobe higher than that of other processing tasks. As a result, theprocessing of the processing task 635 can be restarted in precedence toother processing tasks. The processing task 635 the processing of whichhas been restarted produces a message to be transmitted to the managersystem 4 in accordance with a reply from the exchange 3. The message istransmitted through the interface end portion 60 to the manager system4.

The processing task the process of which has been interrupted because ofwaiting for a reply may be finished. In this case, the communicationservice executing section 63 is designed so as to provide a responsemessage producing section 637.

The response message producing section 637 has a function for producinga message to be transmitted to the manager system 4 instead of theprocessing task waiting for a reply or a reception.

Concretely, upon recognition of the processing task the processing ofwhich has been interrupted because of waiting for a reply or the like,the response message producing section 637 finishes the processing task.Then, upon reception of a reply from the network resource, the responsemessage producing section 637 produces a message to be transmitted tothe manager system 4 on the basis of that reply. That message istransmitted through the interface end portion 60 to the manager system 4(refer to FIG. 29). As a result, the processing delay due to waiting fora reply, a reception or the like can be restrained.

Furthermore, if a relative number between the number of the processingtasks within the communication service executing section 63 and thenumber of the processing tasks within the maintenance service executingsection 64 is increased, a balance in load between the communicationservice executing section 63 and the maintenance service executingsection 64 is liable to be lost. On the contrary, the executingscheduling section 61 may provide a function for monitoring the loadstates of the communication service executing section 63 and themaintenance service executing section 64 to change the precedence degreeof the communication service executing section 63 and the maintenanceservice executing section 64. In other words, the precedence degree ofthe maintenance service executing section 64 is normally set to be lowerthan the precedence degree of the communication service executingsection 63. However, if the load of the maintenance service executingsection 64 is remarkably larger than the load of the communicationservice executing section 63, the executing scheduling section 61 makesthe precedence degree of the maintenance service executing section 64larger than that of the communication service executing section 63.

According to the network element managing system of the presentinvention, a processing request relating to communication can beexecuted at a high speed through a system for maintaining and managingthe network elements such as an exchange or a telecommunication line. Asa result, the system which flexibly copes with a variety of thecommunication services and effectively executes the communicationprocessing can be provided.

Further, the communication control section as well as the managementcontrol section can analyze the processing request and determine anoptimum precedence order in accordance with the attribute of an objectto be processed or the attribute of the processing request. As a result,the system which can effectively execute the processing without anydependency on the protocol of the interface and flexibly cope with avariety of services can be provided.

Still further, in the case of updating data which is redundantly managedby the communication control section and the management control section,the consistency of data between the communication control section andthe management control section can be ensured, thereby realizing therenewal processing at a high speed and with efficiency.

What is claimed is:
 1. A network element managing systemcomprising:manager means for managing a plurality of network elementsincluding an exchange or a telecommunication line which constitutes atelecommunication network to transmit a processing request from aspecified subscriber to a corresponding network element; agent means foranalyzing the processing request transmitted from said manager means todiscriminate whether the processing request is a processing requestrelating to maintenance/management of the network or a processingrequest relating to a communication processing, said agent meansconverting the processing request into a command form which is capableof being processed by the network element to transmit the convertedprocessing request to the network element and to transmit the executionresult of said processing request to said manager means if theprocessing request is of the processing request relating to thecommunication processing; wherein said agent means includes a schedulingsection for delivering data with respect to said manager means todiscriminate whether the communication processing received by saidmanager means is a processing request relating to maintenance/managementof the network or a processing request relating to the communicationprocessing, if said processing request is of the processing requestrelating to the communication processing, said scheduling sectionassigning a precedence order higher than that of the processing requestrelating to the maintenance/management to the processing request, and ifsaid processing request is of the processing request relating to themaintenance/management of the network, said scheduling section assigninga precedence order lower than that of processing request relating to thecommunication processing to the processing request; and an operationprocessing section which executes said processing request according to aprecedence order determined by said scheduling section if saidprocessing request is of a processing request relating to themaintenance/management of the network, converts said processing requestinto a command form which is capable of being processed by the networkelement to allow the network element to execute the processing requestafter conversion according to a precedence order determined by saidscheduling section, and to transmit the execution result to said managermeans; and wherein said operation executing section includescommunication control section which allows said network element toexecute the processing request relating to the communication processingto transmit the execution result to said manager means; and a managementcontrol means for executing the processing request relating to themaintenance/management of said network to transmit the execution resultto said manager means.
 2. A network managing system as claimed in claim1, wherein said management control means includes an object data storingsection for storing a resource identifier for specifying the respectiveresources within said network, an object identifier where the respectiveresources have been converted into logic models and attribute data ofthe respective resources, andwherein said management control sectionexecutes a step of extracting the object identifier of the resource tobe processed from the processing request; a step of retrieving saidobject data storing section on the basis of said object identifier toread the attribute information of said resource; and a step oftransmitting said attribute information to said manager means.
 3. Anetwork element managing system as claimed in claim 2, wherein saidobject data storing section has an attribute information including theoperation history of said respective resources.
 4. A network elementmanaging system as claimed in claim 2, wherein said object data storingsection includes a precedence degree table for storing a precedencedegree which determines the execution order of the processing request tothe respective objects, andwherein said management control sectionincluding a processing content analyzing section, upon receiving theprocessing request relating to maintenance/management from said managermeans, for detecting an object identifier of the object to be processedfrom the processing request and retrieving said precedence degree tableon the basis of the object identifier to judge the precedence degree ofsaid processing request; a processing task producing section forproducing the processing task which executes said processing request;and a processing task scheduling section for starting said processingtask on the basis of the precedence degree which is judged by saidprocessing content analyzing section.
 5. A network element managingsystem as claimed in claim 4, wherein said processing task schedulingsection, when restarting the processing of the processing task which hasbeen interrupted, sets the execution order of said processing task to behigher than that other processing tasks.
 6. A network element managingsystem as claimed in claim 4, wherein said management control sectionfurther includes a response message producing section, upon recognitionof a processing task the processing of which is interrupted because ofwaiting for information from the network element, for forcedly finishingsaid processing task and receives information from said network elementinstead of said processing task to produce a message to be transmittedto said manager means on the basis of that information.
 7. A networkelement managing system as claimed in claim 1, wherein saidcommunication control section includes an object managing table forregistering a resource identifier every object identifier; andwhereinsaid communication control section executes, upon reception of aprocessing request relating to the communication process from saidmanager means, a step of extracting the object identifier of a resourceto be processed from said processing request; a step of retrieving saidobject managing table on the basis of said object identifier to read theresource identifier of said resource; a step of converting saidprocessing request into a command form which can be processed by saidnetwork element on said resource identifier; a step of allowing saidnetwork element to execute the processing request converted; and a stepof transmitting the execution result of said processing request to saidmanager means.
 8. A network element managing system as claimed in claim7, wherein said communication control section executes a step ofrequesting said management control section to update the object datastoring section on the basis of the execution result of said networkelement; and a step of updating said object managing table.
 9. A networkelement managing system as claimed in claim 7, wherein said objectmanaging table includes a precedence degree table for storing theprecedence degree which determines the execution order of the processingrequest with respect to the respective objects, andwherein saidcommunication control section includes a processing content analyzingsection, upon receiving a processing request relating to communicationfrom said manager means, detects an object identifier to be processedfrom the processing request to retrieve said precedence degree table onthe basis of the object identifier to judge the precedence degree ofsaid processing request; a processing task producing section forproducing the processing task which executes said processing request;and a processing task scheduling section for starting said processingtask on the basis of the precedence degree which is judged by saidprocessing content analyzing section.
 10. A network element managingsystem as claimed in claim 9, wherein said processing task schedulingsection, when restarting the processing of the processing task which hasbeen interrupted, sets the execution order of said processing task to behigher than that other processing tasks.
 11. A network element managingsystem as claimed in claim 9, wherein said communication control sectionfurther includes a response message producing section, upon recognitionof a processing task the processing of which is interrupted because ofwaiting for information from the network element, for forcedly finishingsaid processing task and receives information from said network elementinstead of said processing task to produce a message to be transmittedto said manager means on the basis of that information.
 12. A networkelement managing system as claimed in claim 1, wherein said schedulingsection monitors the processing state of said communication controlsection and the processing state of said management control section, ifthe load of said management control section becomes larger than the loadof said communication control section, an execution time higher in aprecedence order than the processing request relating to thecommunication processing is assigned to the processing request relatingto maintenance/management.
 13. A network element managing system,comprising the steps of:upon receiving a renewal request of an objectmanaging table from a manager means, discriminating data to be updatedto discriminate whether the data is in an access prohibition state, ornot; if said data is in an accessible state, then prohibiting access tosaid data from the interior of the communication control section andaccess to said data from the exterior of the communication controlsection; transmitting the processing request to a network element toreceive a reply therefrom if necessary; updating said data on the basisof said renewal request; releasing the prohibition of access to saidaccess from the interior of the communication control section; notifyingsaid manager means of the completion of said data renewal; transferringsaid data renewal request to a management control section; and uponreceiving the completion of execution of the renewal request from saidmanagement control section, releasing the prohibition of access to saiddata from the exterior of said communication control section.
 14. Anetwork element managing system as claimed in claim 13, wherein saidmanagement control section executes, upon receiving said renewal requestfrom said communication control section, a step of prohibiting access tosaid data to be updated which has been stored in said object datastoring section;a step of updating said data on the basis of saidrenewal request; a step of releasing the prohibition of access to saiddata; and a step of notifying said communication control section of thecompletion of execution of said renewal request.
 15. A network elementmanaging system, wherein a management control section executes the stepsof:upon receiving a renewal request of a object data storing sectionfrom a manager means, discriminating data to be updated anddiscriminating whether said data has been also stored in the objectmanaging table of a communication control section, or not; if said datahas been stored in said object managing table, requesting saidcommunication control section to prohibit access to said data; uponreceiving a notice of execution of prohibiting access to said data fromsaid communication control section, converting said data in said objectdata storing section into an access prohibition state; issuing aprocessing request to said network element and receiving a reply to saidprocessing request, if necessary; notifying said communication controlsection of said renewal request; upon receiving a notice of the renewalcompletion from said communication control section, updating said datawhich has been stored in said object data storing section; changing saiddata in said object data storing section from an access prohibitionstate into an accessible state; and notifying said manager means of saidrenewal completion.
 16. A network element managing system as claimed inclaim 15, wherein said communication control section executes the stepsof:discriminating data to be access-prohibited and discriminatingwhether said data is in an access prohibition state, or not; if saiddata is in an accessible state, prohibiting access to said data from theinterior of the communication control section and from the exterior ofthe communication control section, and notifying said management controlsection of the execution of prohibiting access; upon receiving a renewalrequest of said data from said management control section, updating saiddata on the basis of that renewal request; releasing the prohibition ofaccess to said data from the interior of the communication controlsection; notifying said management control section of the renewalcompletion of said data; upon receiving a notice of the renewalcompletion of said data from said management control section, releasingthe prohibition of access to said data from the exterior of thecommunication control section; and if said data is in the accessprohibition state, notifying said management control section of an errorof execution of the access prohibition.